<?xml version="1.0" encoding="ISO-8859-1"?>
<metadatalist>
	<metadata ReferenceType="Journal Article">
		<site>mtc-m21c.sid.inpe.br 806</site>
		<holdercode>{isadg {BR SPINPE} ibi 8JMKD3MGPCW/3DT298S}</holdercode>
		<identifier>8JMKD3MGP3W34R/3R8FB55</identifier>
		<repository>sid.inpe.br/mtc-m21c/2018/06.04.17.02</repository>
		<lastupdate>2018:06.04.17.02.10 urlib.net/www/2017/11.22.19.04 simone</lastupdate>
		<metadatarepository>sid.inpe.br/mtc-m21c/2018/06.04.17.02.10</metadatarepository>
		<metadatalastupdate>2021:02.11.21.04.48 sid.inpe.br/bibdigital@80/2006/04.07.15.50 administrator</metadatalastupdate>
		<doi>10.2514/1.I010525</doi>
		<issn>2327-3097</issn>
		<citationkey>GreghiMarCarAmbVil:2018:AdDr</citationkey>
		<title>From natural language standard documents to state machines: advantages and drawbacks</title>
		<year>2018</year>
		<month>May</month>
		<typeofwork>journal article</typeofwork>
		<secondarytype>PRE PI</secondarytype>
		<numberoffiles>1</numberoffiles>
		<size>650 KiB</size>
		<author>Greghi, Juliana Galvani,</author>
		<author>Martins, Eliane,</author>
		<author>Carvalho, Ariadne M. B. R.,</author>
		<author>Ambrosio, Ana Maria,</author>
		<author>Villani, Emília,</author>
		<resumeid></resumeid>
		<resumeid></resumeid>
		<resumeid></resumeid>
		<resumeid>8JMKD3MGP5W/3C9JGH7</resumeid>
		<group></group>
		<group></group>
		<group></group>
		<group>DIDSS-CGETE-INPE-MCTIC-GOV-BR</group>
		<affiliation>Universidade Federal de Lavras (UFLA)</affiliation>
		<affiliation>Universidade Estadual de Campinas (UNICAMP)</affiliation>
		<affiliation>Universidade Estadual de Campinas (UNICAMP)</affiliation>
		<affiliation>Instituto Nacional de Pesquisas Espaciais (INPE)</affiliation>
		<affiliation>Instituto Tecnológico de Aeronáutica (ITA)</affiliation>
		<electronicmailaddress></electronicmailaddress>
		<electronicmailaddress></electronicmailaddress>
		<electronicmailaddress></electronicmailaddress>
		<electronicmailaddress>ana@dss.inpe.br</electronicmailaddress>
		<journal>Journal of Aerospace Information Systems</journal>
		<volume>15</volume>
		<number>5</number>
		<pages>271-281</pages>
		<transferableflag>1</transferableflag>
		<contenttype>External Contribution</contenttype>
		<versiontype>publisher</versiontype>
		<abstract>Problems in requirements documents are among the root cause of a number of accidents in space missions. A common approach toward the minimization of these problems is to transform the requirements into models that represent the system's behavior. However, this solution requires dealing with issues such as choosing the best modeling formalism, defining to what extent the transformation process should be automated, and assuring the quality of the requirements documents to be used as input. In space missions, requirements are frequently tailored from standard documents, such as the Packet Utilization Standard, which are composed of mandatory and optional requirements. This paper presents a semi-automatic method to transform standard requirements documents into extended finite state machines. To evaluate it, we apply the method to a set of requirements from the Packet Utilization Standard. We evaluate the method using some Packet Utilization Standard services. In light of the results, the paper discusses advantages and potential problems of each approach.</abstract>
		<area>ETES</area>
		<language>en</language>
		<targetfile>greghi_from.pdf</targetfile>
		<usergroup>simone</usergroup>
		<readergroup>administrator</readergroup>
		<readergroup>simone</readergroup>
		<visibility>shown</visibility>
		<readpermission>deny from all and allow from 150.163</readpermission>
		<documentstage>not transferred</documentstage>
		<nexthigherunit>8JMKD3MGPCW/446B2HE</nexthigherunit>
		<citingitemlist>sid.inpe.br/bibdigital/2021/02.11.21.02 2</citingitemlist>
		<citingitemlist>sid.inpe.br/mtc-m21/2012/07.13.14.39.50 1</citingitemlist>
		<dissemination>WEBSCI; SCOPUS.</dissemination>
		<hostcollection>urlib.net/www/2017/11.22.19.04</hostcollection>
		<username>simone</username>
		<agreement>agreement.html .htaccess .htaccess2</agreement>
		<lasthostcollection>urlib.net/www/2017/11.22.19.04</lasthostcollection>
		<url>http://mtc-m21c.sid.inpe.br/rep-/sid.inpe.br/mtc-m21c/2018/06.04.17.02</url>
	</metadata>
</metadatalist>